Frequently Asked Questions about SETI@home

General questions about SETI@home and getting started

1.1. What do I need to participate in SETI@home?
1.2. Do I need to know anything about science or SETI to use SETI@home?
1.3. How long will it take to download the screensaver?
1.4. I pay by the hour for Internet connection. How much connect time will SETI@home need?
1.5. Why are you doing this as a screensaver instead of a background task that runs all the time?
1.6. Why aren't you doing this in Java?
1.7. What about security?
1.8. Will the screensaver program use more than one processor on a multiprocessor machine?
1.9. Why don't you release the source code?
1.10. How complex is the software? Will users have to get involved with switching it on and off, or sending off the results? Will my computer have to be on-line the whole time?
1.11. Are there any issues concerning the SETI@home software and firewalls (or proxies)?
1.12. I downloaded the software but my computer doesn't know what to do with a .tar file - what do I do?
1.13. Can I run this on as many machines as I like?
1.14. What happens to work units that never get returned by us? Are they lost forever?

Questions about running the SETI@home software

2.1. I've been running SETI@home for a while, but after upgrading my client software to the latest version, work units take eight times longer to process! Am I doing anything wrong?
2.2. According to your stats page platform X is running Y times faster than me! Why?
2.3. What happened to the gaussian information display in the new Mac and Windows clients? Are the clients still looking for gaussians?
2.4. I have SETI@home set to run as my screen saver, but it keeps getting interrupted right after it starts running. What is going on?
2.5. How do I change my login address/user info?
2.6. Is the Windows screensaver password protected?
2.7. I'm trying to connect through a HTTP proxy server running at a port other server running at a port other than port 80 and am unable to connect.
2.8. The client reports that it is unable to connect to the server. On Windows 95/98/NT machines this is sometimes seen as a WinSOCK error number 10060.

Questions about SETI@home science

3.1. What will happen if an extraterrestrial signal is detected?
3.2. Will I get credit if the signal is detected using my computer?
3.3. It says SETI@home will run for 2 years. Why not keep it going indefinitely?
3.4. If you find a signal, how will you decode the information in it?
3.5. How is data collected from the telescope and transmitted to other machines for analysis?
3.6. Will you ship larger chunks of data to faster computers?
3.7. What sorts of signals are being analysed, and what form does the signal analysis take?
3.8. How will the results of the calculations be merged again?
3.9. Are there any safeguards in place that would prevent the sending of a false 'negative' interpretation of data, thus masking an extraterrestrial signal?
3.10. What is to prevent someone from hacking the program and sending back false data that would interpret a signal as extraterrestrial?
3.11. Is it likely that so many people sign up that you won't always have enough Arecibo data to feed all the clients? If so, how will this be handled?

Questions about SETI in general

4.1. What sort of spectrum is currently being emitted by earth? Is that signal visible say 10 or 50 light years away? If SETI were on a planet say 10-50 light years from here and running this project there, would it be able to detect earth's signal (assuming it was looking in our direction)?


General questions about SETI@home and getting started


1.1. What do I need to participate in SETI@home?

You'll need a computer with at least 32 MB of RAM, 10 MB of disk space, and an Internet connection (dialup is OK). You can use SETI@home on a laptop that is connected sporadically. We plan to support Win95, Win98, WinNT, Mac, and many versions of UNIX, including Linux on various CPUs. We hope to eventually support other systems such as OS/2 and BeOS. We won't support WebTV. There are no CPU speed or modem speed requirements. It doesn't matter where in the world you live.


1.2. Do I need to know anything about science or SETI to use SETI@home?

No. All you need to do is download and install the client software.


1.3. How long will it take to download the screensaver?

About 5 minutes over a 28.8Kbps modem.


1.4. I pay by the hour for Internet connection. How much connect time will SETI@home need?

SETI@home connects only when transferring data. This occurs once every few days and lasts for about 5 minutes.


1.5. Why are you doing this as a screensaver instead of a background task that runs all the time?

SETI@home uses a lot of memory while it's running, and it would cause swapping on some computers. We want to make sure it has zero impact on your normal computer work. So, for PC and Mac, the default mode is screensaver.

However, if you already have a favorite screensaver, or prefer not to run a screensaver, SETI@home can also be run as a background program that computes all the time and has no graphics. The UNIX version works like this.


1.6. Why aren't you doing this in Java?

It's not currently fast enough, and there are lots of system-dependent details that we need to handle in C.


1.7. What about security?

The screensaver will be available for download only from our web server, and it will upload and download data only from our data server. The data server doesn't download any executable code. All in all, the screensaver will be much safer than the browser you're running right now!


1.8. Will the screensaver program use more than one processor on a multiprocessor machine?

Not the initial version. Maybe a subsequent one.


1.9. Why don't you release the source code?

We decided not to make source code available for security reasons and for science reasons as well. We have to have everyone do the exact same analysis, or we can't have any control over our research and be confident in our results. We were also worried that there may be a few people that want to deliberately try to screw up our database and server.


1.10. How complex is the software? Will users have to get involved with switching it on and off, or sending off the results? Will my computer have to be on-line the whole time?

Users will not have to do anything if they don't want. The results can be sent automatically, next time the users are on the internet (checking their mail, surfing, etc), or it can be set to ask permission before logging on to the internet.


1.11. Are there any issues concerning the SETI@home software and firewalls (or proxies)?

SETI@home uses the HTTP protocol, and should work through any semi-transparent firewall that allows outgoing Web traffic. We are currently working on making SETI@home work through more restrictive firewalls and proxies.


1.12. I downloaded the software but my computer doesn't know what to do with a .tar (or .sit or .exe) file - what do I do?

Windows software is packaged in files ending with .exe, Mac software with .sit, and UNIX with .tar - chances are you have downloaded software for a system other than yours.


1.13. Can I run this on as many machines as I like?

Yes, you can - and as long as you use the same login on each machine, you'll get credit for them all.

Please note that you can (currently) only run one SETI@home process on a Windows or Mac machine, and if you are running multiple SETI@home UNIX processes, they must be running out of different directories.


1.14. What happens to work units that never get returned by us? Are they lost forever?

We keep track of every work unit that goes out - if it is taking too long getting the results back, we'll send it out to somebody else. Only after we get results back and confirm them we will remove the work unit from disk.


Questions about running the SETI@home software


2.1. I've been running SETI@home for a while, but after upgrading my client software to the latest version, work units take eight times longer to process! Am I doing anything wrong?

Not to worry. This is completely normal as the newer clients have updated science code which looks at the data in more detail that previous clients. This increase in the actual science done by the clients requires more CPU time.

By the way, different operating systems and different CPU types can run at vastly different speeds. Some may process work units in a matter of hours while some may take days.


2.2. According to your stats page platform X is running Y times faster than me! Why?

See 2.1. above - newer versions are running slower, yet people are still running older versions to "up their stats." This is a moot point since we'll be zero-ing out the database come the official launch date.


2.3. What happened to the gaussian information display in the new Mac and Windows clients? Are the clients still looking for gaussians?

The clients are still looking for Gaussions, however rather than display information about gaussions all the time, in newer clients the information only appears if the client has found something interesting to report.


2.4. I have SETI@home set to run as my screen saver, but it keeps getting interrupted right after it starts running. What is going on?

The SETI@home client may be being interrupted by another screen saver or screen saver-like program. As SETI@home is designed to be as noninvasive as possible by only using your computer while it is idle, if the client detects another program that wants to run, SETI@home will quit and step out of the way. If this other program is another screen saver or some other application that waits until your computer is idle before running, both SETI@home and the other program will try to run when the computer is idle causing SETI@home to quit. One common application which shows this behavior is McAfee VirusScan. If you have VirusScan installed, make sure that you have turned off the ScreenScan portion of the application as this will interfere with SETI@home.


2.5. How do I change my login address/user info?

Currently there is no way to do this. Eventually there will be an automated web-based mechanism for which you can submit a "change request", get a temporary password, and then you can change your info. We need this added level of security to make sure people don't haphazardly change other users' information.


2.6. Is the Windows screensaver password protected?

Our screensaver works just like any other screensaver, which includes the ability for the operating system to enforce password protection. This is done through the normal password protection channels.


2.7 I'm trying to connect through a HTTP proxy server running at a port other than port 80 and am unable to connect.

This is a known bug within the 1.0 release of the software. We are currently working on a fix which should be out by May the 21st.


2.8 The client reports that it is unable to connect to the server. On Windows 95/98/NT machines this is sometimes seen as a WinSOCK error number 10060.

Due to overwhelming interest in the SETI@home project, the server may intermittently be unreachable as too many clients are trying to connect. The server may also be occasionally down for maintainance. If you are unable to connect, please wait an hour and try again.


Questions about SETI@home science


3.1. What will happen if an extraterrestrial signal is detected?

A procedure has been agreed upon by SETI researchers around the world. First, other SETI researchers will independently verify the signal. If the signal is real and can't be explained by man-made sources (satellites, reflections etc.) then press agencies and governments will be notified in a systematic way.


3.2. Will I get credit if the signal is detected using my computer?

Yes. Our software keeps track of where each piece work is done. If your computer is involved in the detection, you will, if you wish, be listed as a co-discoverer.


3.3. It says SETI@home will run for 2 years. Why not keep it going indefinitely?

In 2 years the Arecibo radio telescope will have scanned the part of the sky visible to it three times, and SETI@home will have analyzed this data. That's enough for our purposes. And by then there will be new telescopes, new experiments, and new approaches to SETI.


3.4. If you find a signal, how will you decode the information in it?

Our goal is simply to find the signal. If it contains information, it may require experts in linguistics or mathematics to decipher it.


3.5. How is data collected from the telescope and transmitted to other machines for analysis?

Data will be recorded on high density tapes at the Arecibo telescope in Puerto Rico, about one 35 Gbyte tape per day, then mailed to Berkeley, then divided into 0.25 Mbyte chunks which get sent from the Seti@Home server over the internet to people around the world to analyse. Arecibo does not have a high bandwidth internet connection, so data must go by snail mail to Berkeley at first.


3.6. Will you ship larger chunks of data to faster computers?

No, all computers receive the same size chunks. Faster computers will finish each chunk faster, then immediately get a new chunk to work on, so we'll keep them busy all the time.


3.7. What sorts of signals are being analysed, and what form does the signal analysis take?

We search for strong narrow band signals. It's like tuning your radio set to various channels, and looking at the signal strength meter. If the strength meter goes up, that gets our attention. More technically, it's a lot of digital signal processing, mostly Fourier Transforms at various chirp rates and durations.

We also search for pulsing and drifting signals, and signals which match the antenna beam pattern as the telescope slews across the sky. The analysis software searches for signals about 10 times weaker than any search done to date, because it makes use of a computationally intensive algorithm called "coherent integration" that no one else (including our Serendip program) has had the computing power to implement.


3.8. How will the results of the calculations be merged again?

They are merged in a database using our computers here, interference is rejected, and various pattern detection algorithms are applied to search for the most interesting signals.


3.9. Are there any safeguards in place that would prevent the sending of a false 'negative' interpretation of data, thus masking an extraterrestrial signal?

Yes. Without going into detail (for obvious reasons) we have a mechanism that detects forged results.


3.10. What is to prevent someone from hacking the program and sending back false data that would interpret a signal as extraterrestrial?

See the above question. Besides, it wouldn't matter - if there's a "hit", we will analyze that chunk of data ourselves to verify it.


3.11. Is it likely that so many people sign up that you won't always have enough Arecibo data to feed all the clients? If so, how will this be handled?

It's possible. Up to a point, we will handle it by sending the same data to more than one user. Beyond that, if we can afford it, we will set up another data recorder at Arecibo and record a wider frequency range (our current system records only 2.5 MHz out of SERENDIP's 100 MHz bandwidth).


Questions about SETI in general


4.1. What sort of spectrum is currently being emitted by earth? Is that signal visible say 10 or 50 light years away? If SETI were on a planet say 10-50 light years from here and running this project there, would it be able to detect earth's signal (assuming it was looking in our direction)?

Earth is polluting space with radio and television signals that might be detected by nearby advanced civilizations, but it would be difficult for such a civilization to discover these signals if they only have Earth's current level of technology (eg: if they have an Arecibo like telescope and SETI@home like search).

Early TV shows like I Love Lucy and Ed Sullivan left the earth about 40 years ago, so have gone out 40 light years, reaching several thousand nearby stars. But these signals are relatively weak and SETI@home is not likely to detect the equivalent of Earth type TV transmitters, even on the nearest stars.

Earth's strongest transmitters might be somewhat easier to detect, such as those emitted by military radars, or some radio telescopes. The Arecibo telescope transmits very powerful signals when it is used as a radar system to study planets, asteroids and the ionosphere. These radar signals are powerful enough to be detected 10,000 light years away by searches like SETI@home, except for three big caveats:

a) The Arecibo transmissions are in a very tight beam (they are not omnidirectional, like TV and military radar), so they only cover a very small part of the sky at once (about a millionth of the total sky). It's is unlikely another civilization will be within one of these narrow beams.

b) The Arecibo transmitter's oldest signals left Earth about 30 years ago, so have only travelled 30 light years.

c) SETI@home is not searching the band of frequencies that the Arecibo transmitters utilize (although our older SERENDIP III program did survey one of those bands).


Back to the top of this page

Back to the home page